http: don't emit 'readable' after 'close'#32277
Closed
ronag wants to merge 3 commits intonodejs:masterfrom
Closed
Conversation
Collaborator
Member
Author
|
I guess optimally |
600401d to
c48885a
Compare
Member
Author
|
@nodejs/http |
Collaborator
Collaborator
Collaborator
jasnell
reviewed
Mar 19, 2020
jasnell
reviewed
Mar 19, 2020
Member
Author
|
@nodejs/http |
Collaborator
Member
Author
|
Suspicious failure on CI. |
Collaborator
addaleax
approved these changes
Mar 29, 2020
jasnell
approved these changes
Mar 29, 2020
Collaborator
Collaborator
Collaborator
Collaborator
Member
|
Landed in e034f5c |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An edge case could emit 'readable' after 'close' and 'close' before 'end'.
Refs: #28710
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes